Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1412

reference: 530-tree-1
name: 1412
tree-preservation-order: undefined
530-tpo-1
uprn
address-text
point: POINT (-1.016805 50.897831)
geometry: MULTIPOLYGON (((-1.016776 50.897828,-1.016777 50.897834,-1.016781 50.897839,-1.016788 50.897843,-1.016804 50.897846,-1.016821 50.897843,-1.016832 50.897834,-1.016833 50.897828,-1.016832 50.897823,-1.016828 50.897818,-1.016822 50.897814,-1.016814 50.897811,-1.016805 50.897810,-1.016788 50.897813,-1.016782 50.897817,-1.016778 50.897822,-1.016776 50.897828)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL